What

Reclassifies bridge-db and notification-hub as infrastructure in the portfolio catalog and records the portfolio attention reconciliation note.

Why

The live portfolio truth snapshot still classified both operating-layer repos as vanity / manual-only, while the reconciliation intent expected them to resolve as active infrastructure. The normal publish path now confirms both resolve as active-infra with Notion context preserved.

Review Of What Was Built

• Updated config/portfolio-catalog.yaml so bridge-db and notification-hub use category: infrastructure.
• Added scoped notes to keep weekly attention constrained to concrete bridge, sync, health, cross-system state, runtime, or operator-signal decisions.
• Added docs/plans/2026-06-14-portfolio-attention-reconciliation.md with the original blocker and the successful 2026-06-19 publish result.

Cleanup Review

No generated output/* artifacts are committed; those remain ignored local truth outputs. No Notion data was mutated.

Verification Summary

• uv run python -m src.cli report saagpatel --portfolio-truth
• jq row check confirmed bridge-db and notification-hub are category=infrastructure, attention_state=active-infra, notion_current_state=Shipped.
• jq snapshot check confirmed source_summary.notion_context_rows=137 and warnings=[].
• uv run pytest -q tests/test_portfolio_truth.py tests/test_catalog_validator.py: 56 passed, 1 existing deprecation warning.
• uv run ruff check .: passed.

Shipped Summary

The branch records the catalog source-of-truth change and the reconciliation note that explains why the generated local truth moved from manual-only to active-infra for these two repos.

Next Phase

After merge, any downstream local surfaces that consume output/portfolio-truth-latest.json should read the already-regenerated local snapshot or rerun the normal publish command with Notion context available.

Remaining Roadmap

No broader portfolio reactivation is included; this PR is intentionally limited to bridge-db and notification-hub.